The Atari Compendium

home *** CD-ROM | disk | FTP | other *** search

/ The Atari Compendium / The Atari Compendium (Toad Computers) (1994).iso / files / netbsd / install.txt < prev next >

Wrap

Text File | 1996-01-12 | 41.8 KB | 1,139 lines

INSTALLATION NOTES for NetBSD/atari 1.1 Be sure to read _ALL_ of this document before you try to install NetBSD/atari. What is NetBSD? ---- -- ------ NetBSD is a Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite -derived Operating System. It is a fully functional UN*X-like system which runs on many architectures and is being ported to more. NetBSD, as the name implies, is a creation of the members of the network community and without the net it's likely that this release wouldn't have come about. NetBSD 1.1 is a evolutionary release which contains over a year of changes to the kernel, user-level utilities, and documentation. Continuing the multi-platform tradition, NetBSD has added ports to atari and mvme68k based machines. Kernel interfaces have continued to be refined, and now several subsystems and device drivers are shared among the different ports. You can look for this trend to continue. NetBSD 1.1 has significantly enhanced the binary emulation subsystem (which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix compatibility) and several kernel subsystems have been generalized to support this more readily. The binary emulation strategy is aimed at making the emulation as accurate as possible. NetBSD 1.1 is also the first release to see machine-independent disk striping. The concatenated disk driver (ccd), which was previously supported only by the hp300 port, has been vastly improved. Many bugs were fixed, and explicit references to device-dependent routines removed and replaced by calls to the generic "vnode operation" routines. In addition, several features were added, including partition support, dynamic configuration and unconfiguration via a user space system utility program, and virtually unlimited number of component devices. Many new user programs have been added in NetBSD 1.1, as well, bringing it closer to our goal of supplying a complete UN*X-like environment. The Atari release stepped in in March 1995. This means the NetBSD1.1 is the first official release of NetBSD/Atari. The Future of NetBSD: --- ------ -- ------ The NetBSD Foundation was recently incorporated as a non-profit organization. It's purpose is to encourage, foster and promote the free exchange of computer software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project. (IN WHAT WAY? Money, donations, etc) We believe that the NetBSD Foundation will help improve the quality of NetBSD by: * providing better organization to keep track of development efforts, including co-ordination with groups working in related fields. * providing a framework to receive donations of goods and services and to own the resources necessary to run the NetBSD Project. * providing a better position from which to undertake promotional activities. * periodically organizing workshops for developers and other interested people to discuss ongoing work. We hope to have regular releases of the full binary and source trees, but these are difficult to coordinate, especially with all of the architectures which we now support! We hope to support even _more_ hardware in the future, and have a rather large number of other ideas about what can be done to improve NetBSD. We intend to continue our current practice of making the NetBSD-current development source available on a daily or nearly-daily basis. We intend to integrate free, positive changes from whatever sources will provide them, providing that they are well thought-out and increase the usability of the system. Above all, we hope to create a stable and accessible system, and to be responsive to the needs and desires of NetBSD users, because it is for and because of them that NetBSD exists. Sources of NetBSD: ------- -- ------ Host name Services Provided ---- ---- -------- -------- ftp.iastate.edu Anonymous FTP, AFS Anon-FTP path: pub/netbsd AFS path: /afs/iastate.edu/public/ftp/pub/netbsd ftp.eecs.umich.edu Anonymous FTP Anon-FTP path: BSD/NetBSD gatekeeper.dec.com Anonymous FTP Anon-FTP path: pub/BSD/NetBSD wipux2.wifo.uni-mannheim.de Anonymous FTP, SUP Anon-FTP path: pub/NetBSD SUP: get the file pub/misc/sup/supfile.example via anonymous FTP and read it as an example. ftp.demon.co.uk Anonymous FTP, possibly SUP Anon-FTP path: pub/BSD/NetBSD SUP: contact peter@demon.net for SUP server status/information ftp.uni-regensburg.de Anonymous FTP Anon-FTP path: pub/NetBSD ftp.unit.no Anonymous FTP Anon-FTP path: pub/NetBSD ftp.stacken.kth.se Anonymous FTP Anon-FTP path: pub/OS/NetBSD flick.lerc.nasa.gov Anonymous FTP Anon-FTP path: pub/NetBSD coombs.anu.edu.au Anonymous FTP Anon-FTP path: pub/NetBSD ftp.funet.fi Anonymous FTP Anon-FTP path: pub/unix/NetBSD ftp.netbsd.org Anonymous FTP, SUP Anon-FTP path: pub/NetBSD SUP: get the file pub/sup/README.sup via anonymous FTP from ftp.netbsd.org, and read it for instructions. If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org. NetBSD 1.1 Release Contents: ------ --- ------- -------- The NetBSD 1.1 release is organized in the following way: .../NetBSD-1.1/ BUGS Known bugs list (incomplete and out of date). CHANGES Changes since NetBSD's last release (and before). LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.1 distribution. README.files README describing the distribution's contents. TODO NetBSD's todo list (incomplete and out of date). patches/ Post-release source code patches. source/ Source distribution sets; see below. In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures that NetBSD 1.1 has a binary distribution for. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (e.g. those containing crypt(3)) that should not be exported from the United States, and that if you do export them, it's your fault, not ours. The source distribution sets can be found in subdirectories of the "source" subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows: dsrc11 This set contains the "domestic" sources. These sources contain export-restricted encryption code and should not be exported from the U.S. [ 140K gzipped, 655K uncompressed ] gsrc11 This set contains the "gnu" sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. [ 7.1M gzipped, 30.4M uncompressed ] ksrc11 This set contains the sources to the NetBSD 1.1 kernel, config(8), config.old(8) and dbsym(8). [ 6.0M gzipped, 27.0M uncompressed ] ssrc11 This set contains the "share" sources, which include the sources for the man pages not associated with any particular program, the sources for the typesettable document set, the dictionaries, and more. [ 2.4M gzipped, 8.9M uncompressed ] src11 This set contains all of the NetBSD 1.1 sources which are not mentioned above. [ 9.3M gzipped, 41.6M uncompressed ] It is worth noting that unless all of the source distribution sets are installed (except the domestic set), you can't rebuild and install the system from scratch, straight out of the box. However, all that is required to rebuild the system in that case is a trivial modification to one Makefile. The source distribution sets are distributed as groups of files named "set_name.xx" where "set_name" is the distribution set name, and "xx" is the sequence number of the file, starting with "aa" for the first file in the distribution set, then "ab" for the next, and so on. All of these files except the last one of each set should be exactly 240,640 bytes long. (The last file is just long enough to contain the remainder of the data for that distribution set.) Catted together, the files belonging to a source distribution set comprise a gzipped tar file. If you want to look at list of the files contained in the set, you could use the command: cat set_name.?? | gunzip | tar tvf - or to actually extract the files contained in the set: cat set_name.?? | gunzip | tar xfp - In each of the source distribution set directories, there is a file named "CKSUMS" which contains the checksums of the files in that directory, as generated by the cksum(1) utility. You can use cksum to check the integrity of the archives, if you suspect that one of the files is corrupt and have access to a cksum binary. The Atari-specific portion of the NetBSD 1.1 release is found in the "atari" subdirectory of the distribution. That subdirectory is layed out as follows: .../NetBSD-1.1/atari/ binary/ atari binary distribution sets; see below. floppies/ atari boot and installation floppies; see below. security/ atari security distribution; see below; utils.netbsd/ utils.tos/ Miscellaneous atari installation utilities; see installation section, below. There are three atari floppy images to be found in the "atari/floppies" subdirectory of the NetBSD 1.1 distribution. One of them is a bootable TOS kernel floppy and the other two are installation floppy's. They are described in more detail below. There are gzipped versions of each available, for easier downloading. (The gzipped version have the ".gz" extension added to their names.) Bootable Kernel floppy: This TOS disk contains the loadbsd and chg_part programs and the GENERIC kernel. It is setup so that you can insert it int your floppy drive, and start the programs from GEM. This floppy is named boot-11.fs Installation floppy: This disk contains a BSD root file system setup to help you install the rest of NetBSD. This includes formatting and mounting your root and /usr partitions and getting ready to extract (and possibly first fetching) the distribution sets. There is enough on this file system to allow you to make a slip connection, configure an ethernet, mount an NFS file system or ftp. You can also load distribution sets from a SCSI tape or from one of your existing TOS partitions. This floppy's are named "inst-11.fs.1" and "inst-11.fs.2". The NetBSD/atari binary distribution sets contain the binaries which comprise the NetBSD 1.1 release for the atari. There are seven binary distribution sets, and the "security" distribution set. The binary distribution sets can be found in subdirectories of the "atari/binary" subdirectory of the NetBSD 1.1 distribution tree, and are as follows: base11 The NetBSD/atari 1.1 base binary distribution. You MUST install this distribution set. It contains the base NetBSD utilities that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below. [ 7M gzipped, 19M uncompressed ] comp11 The NetBSD/atari Compiler tools. All of the tools relating to C, C++, and FORTRAN (yes, there are two!). This set includes the system include files (/usr/include), the linker, the compiler tool chain, and the various system libraries (except the shared libraries, which are included as part of the base set). This set also includes the manual pages for all of the utilities it contains, as well as the system call and library manual pages. [ 4M gzipped, 12M uncompressed ] etc11 This distribution set contains the system configuration files that reside in /etc and in several other places. This set MUST be installed if you are installing the system from scratch, but should NOT be used if you are upgrading. (If you are upgrading, it's recommended that you get a copy of this set and CAREFULLY upgrade your configuration files by hand.) [ 50K gzipped, 280K uncompressed ] games11 This set includes the games and their manual pages. [ 1M gzipped, 3M uncompressed ] man11 This set includes all of the manual pages for the binaries and other software contained in the base set. Note that it does not include any of the manual pages that are included in the other sets. [ 730K gzipped, 3M uncompressed ] misc11 This set includes the system dictionaries (which are rather large), the typesettable document set, and man pages for other architectures which happen to be installed from the source tree by default. [ 2M gzipped, 6M uncompressed ] text11 This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 784K gzipped, 3M uncompressed ] The atari security distribution set is named "secr11" and can be found in the "atari/security" subdirectory of the NetBSD 1.1 distribution tree. It contains crypt.c (the source file for the DES encryption algorithm) and the binaries which depend on it. It can only be found on those sites which carry the complete NetBSD distribution and that can legally obtain it. (Remember, because of United States law, this distribution set may not be exported to locations outside of the United States and Canada.) [ 119K gzipped, 300K uncompressed ] The atari binary distribution sets are distributed in the same form as the source distribution sets; catted together, the members of a set form a gzipped tar file. Each atari binary distribution set also has its own "CKSUMS" file, just as the source distribution sets do. The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the files are extracted "below" the current directory. That is, if you want to extract the binaries "into" your system, i.e. replace the system binaries with them, you have to run the "tar xvfp" from /. Also note that if you upgrade or install this way, those programs that you are using at the time will NOT be replaced. If you follow the normal installation or upgrade procedures, this will be taken care of for you. NetBSD System Requirements and Supported Devices: ------ ------ ------------ --- --------- ------- NetBSD/atari 1.1 runs on a TT030 and a Falcon. Currently an FPU is required, although this might change in the (near) future. The minimum amount of RAM required is 4Mb. Here is a table of recommended HD partition sizes for a full install: partition: advise, with X, needed, with X root (/) 15M 15M 10M 10M user (/usr) 65M 100M 45M 80M swap ----- 2M for every M ram ----- local (/local) up to you As you may note the recommended size of /usr is 20M greater than needed. This is to leave room for a kernel source and compile tree as you will probably want to compile your own kernel. (GENERIC is large and bulky to accommodate all people, BOOT is small and might not have all the features you want). Supported devices include: - The buildin SCSI host adapter - Should support most SCSI-drives. The drives that are currently tested are: MAXTOR 7245S, MAXTOR 7080S, SEAGATE ST157N - Should support most tape drives. The drives that are currently tested are: TANDBERG 3600 - Should support most CD-ROM drives. - The buildin video controller - The building (720Kb/1.44Mb) floppydrive - The serial2/modem2 ports - The Falcon FX memory expansion - The atari mouse If its not on this list, there is no support for it in this release. Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- Installation is supported from several media types, including: TOS HD partitions Tape No matter what you do, however, you'll need to have three disks handy, on which you will put the install and boot floppy images. All the images are available from the directory "atari/floppies", under the root of the NetBSD tree at your favorite archive site. If you are using NetBSD/atari to make the floppies, you should use the command dd(1) to write the raw floppy images (.fs files) to the disk. To write onto fd0 use: dd if=inst-10.fs.1 of=/dev/rfd0b bs=9b If you are using TOS to make the floppies, grab the 'rawwrite' utility from the "atari/utils" directory and issue the command: rawwrite boot-10.fs This will create the boot-floppy on the floppy in drive a. The floppies should be pre-formatted on 720Kb for both the 'dd' and 'rawwrite' commands to work. Pre-formatting can be best done using the desktop format command. Some other utilities seem to be giving problems. The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. The various methods are explained below. To prepare for installing via an GEMDOS partition: To install NetBSD from an GEMDOS partition, you need to get the NetBSD distribution sets you wish to install on your system on to an GEMDOS partition. All of the set_name.xx pieces can be placed in a single directory instead of separate ones for each distribution set. This will also simplify the installation work later on. Note where you place the files you will need this later. Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. To prepare for installing via a tape: To install NetBSD from a tape, you need to somehow get the NetBSD filesets you wish to install on your system on to the appropriate kind of tape, in tar format. If you're making the tape on a UN*X system, the easiest way to do so is: tar cvf <tape_device> <files> where "<tape_device>" is the name of the tape device that describes the tape drive you're using (possibly something like /dev/nrst0, but we make no guarantees 8-). If you can't figure it out, ask your system administrator. "<files>" are the names of the "set_name.nnn" files which you want to be placed on the tape. Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ Note you will be modifying your HD's if you mess something up here you could lose everything on all the drives that you mess with. It is therefore advised that you: Write down your current configurations. Do this by writing down all partition info (especially their sizes). Back up the partitions you are keeping. What you need to do is partition your drives; creating space for at least root, swap and /usr partitions and possibly at least one more for /local if you have the space. The partitioning can be done in two ways, the first method heavily relies on the AHDI way of partitioning, the second method nearly ignores the AHDI partitioning and gives you far more flexibility. Currently, the second method can only be achieved from a working NetBSD/atari system. How this should be done is described in "upgrading to NetBSD-labeling". Using AHDI partitioning: The paritioning can be done with the AHDI-disk that is provided with your TT or Falcon. Note that the AHDI partioning function erases all partions on your harddisk even if they are not changed! I know this is rather stupid, but don't say I didn't warn you. You will need the 'chg_part' program from the bootdisk to prepare your harddisk a bit more. This program will change the partition-id so NetBSD knows which partitions it can use. The synopsis is: chg_part <driveno> <partno> <new_id> The drive number corresponds with the drive's SCSI-id. The new id can be selected from one of the following acronyms: NBU - NetBSD User partition NBR - NetBSD Root partition NBS - NetBSD Swap partition Because NetBSD cannot be bootloaded (yet) and thus must be loaded through GEM, it is unwise to use drive 'C' (drive 0/partition 1) as a NetBSD partition. When a partition-id is changed, GEMDOS won't be able to recognize your drive, so be warned that the drive labels are shifted afterwards. The chg_part program still recognizes them, take this into account when re-labeling partitions. Also note that the chg_part process is reversible. So don't panic if you made a mistake. Just run chg_part again with the same drive/partition arguments but supplied the original partition id. Upgrading to NetBSD-labeling: First of all the new disk label functions are fully backwards compatible with the current (old) behaviour, therefore you don't have to rename partition identifiers if you don't want to. The only limitation is that you won't be able to write a disklabel to your harddisk ("Device not configured."). If you'ld like to have the flexibility of the NetBSD disk label, the procedure is very simple: change the identifier of the AHDI partition that contains your NetBSD root filesystem from NBR to NBD. Boot NetBSD; run `disklabel -e sd?'; disklabel will start vi; quit vi without changing anything; now the disklabel should be written to the NBD partition. If at this point disklabel tells you that one or more of your partitions extend past the end of the unit, then you have an old version of disklabel. Get the If you like, you can now change the NBD partition id to RAW (this would for example be necessary if the partition must be shared with MiNT), but keep in mind that the partition id must be either NBD or RAW, otherwise NetBSD won't be able to find the disklabel. The NBS id (used for a swap partition) is no longer needed, you can change it to whatever you like (or leave it as is, if that's what you like :-) ). The same is true for the NBU id's. WARNINGS: - the NBD partition does not necessarily have to be the partition that contains the NetBSD root filesystem, but it *must* be a partition that contains a fast filesystem. Do *not* try this with a partition that contains a gemdos, minix or ext2 filesystem; if you do, you'll *loose* a filesystem. - Now that you have a real disklabel, you can modify it in (almost) any way you want. However, if you make a mess of the disk label, NetBSD may (or may not) make a mess of your disk! No freedom without responsibility. NetBSD will try to warn you for a possibly dangerous partition table, but it's up to you to either take that warning serious or ignore it (there may be good reasons to ignore the warning, if you know what you're doing). So what do you do if you have a new disk, that will be exclusively used by NetBSD? Very simple: don't let it get `infected' by the AHDI `virus'. ,-) Just connect the disk to your TT/Falcon; boot NetBSD; run `disklabel -e'; you'll see only one large partiton `d' (there won't be any filesytem on it yet); you can create partitions in any way you want, as you're no longer limited by an AHDI partition table. Installing the NetBSD System: ---------- --- ------ ------ Installing NetBSD is a relatively complex process, but, if you have this document in hand and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble. Before you begin, you must have already prepared your hard disk as detailed in the section on preparing your system for install. The following is a walk-through of the steps necessary to get NetBSD installed on your hard disk. If you wish to stop the installation, you may hit Control-C at any prompt, but if you do, you'll have to begin again from scratch. First you need to get yourself into NetBSD. This can be done in a couple ways, both of which currently require GEMDOS. You can insert the GEMDOS kernel floppy and select the loadbsd program. It will ask for parameters, supply: '-b netbsd'. You can, of course, also run it from the shell command-line in MiNT: loadbsd -b a:/netbsd You should see the screen clear and some information about your system as the kernel configures the hardware. Then you will be prompted for a root device. At this time remove the GEMDOS kernel boot floppy from the drive if present and insert the BSD install floppy 1. Now type `rd0' to tell the kernel to load the install filesystem into RAMdisk. While While the kernel is loading, it will show a '.' for each track loaded. After loading 80 tracks, it will ask you to insert the next floppy. At this time, inser the BSD install floppy 2 and hit any key. The kernel continous loading another 40 tracks before it continues to boot. The system should continue to boot. For now ignore WARNING: messages about bad dates in clocks. Eventually you will be be asked to enter the pathname of the shell, just hit return. After a short while you should see a welcome message and a prompt, asking if you wish to proceed with the installation. If you wish to proceed, enter "y" and then return. If you have configured your hard drive[s] correctly it should find the drive and partition that you selected to use as your root. YOU ARE NOW AT THE POINT OF NO RETURN. If you confirm that you want to install NetBSD, your hard drive will be modified, and perhaps its contents scrambled at the whim of the install program. If you are sure you want to proceed, enter "yes" at the prompt. The install program will now make the root filesystem you specified. There should be only one error in this section of the installation. It will look like so: newfs: ioctl (WDINFO): Invalid argument newfs: /dev/rsd0a: can't rewrite disk label If there are any others, restart from the the beginning of the installation process. This error is ok as the Atari does not write disklabels currently. You should expect this error whenever using newfs. Next the install program will ask you which drive and partition you wish to use as /usr. First it will list the available drives. Choose one. Next it will give you a list of the partitions on that disk along with their sizes, types, etc.. Choose the letter that corresponds to the partition you wish to use for /usr. To be able to make the proper selection, you need to know, that NetBSD assigns a special meaning to some of the partition letters: 'a' : root filesystem 'b' : swap partition 'c' : whole disk You should choose a letter in the range 'd'-'p' for your /usr filesystem. If you are doing a full install this should be a partition that is at least 45M-50M large. If everything is ok the install program will then format and mount your /usr. If not then it will ask again for a drive and partition. When this completes your root partition will be mounted on /mnt and your /usr partition on /mnt/usr. An fstab will have been created and initialized to correctly mount these two file systems. This fstab will be in /mnt/etc. What you do from this point on depends on which media you're using to install NetBSD. Follow the appropriate instructions, given below. To install from an GEMDOS partition: You first need to mount the GEMDOS partition using the mount_msdos command. If e.g. your GEMDOS partition is the first partition on sd0 you could type: mkdir /mnt/gemdos mount_msdos /dev/sd0d /mnt/gemdos You can use `disklabel sd0' to find out what types of partitions are on the disk `sd0'. Next goto the directory in which you stored the distribution sets. If e.g. you stored them in the root directory of the partition: cd /mnt/gemdos When there, run "Set_tmp_dir" and choose the default temporary directory, by hitting return at the prompt. Run the "Extract" command, giving it as its sole argument the name of the distribution set you wish to extract. For example, to extract the base distribution, use the command: Extract base11 and to extract the games distribution: Extract game11 If the distribution sets are in different directories, you will need to cd to each directory in turn, runing "Set_tmp_dir" and the appropriate "Extract" command(s). Continue this process until you've finished installing all of the sets which you desire to have on your hard disk. Once you have extracted all sets and are at the "#" prompt again, proceed to the section "Configuring Your System," below. To install from tape: The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, use the command "Set_tmp_dir" and enter your choice. The default is /mnt/usr/distrib. After you have picked a temporary directory, you should issue the load command: Load_tape Next, you will be told to insert the media into the appropriate drive, and hit return. Continue to follow instructions until you are returned to the "#" prompt. Go to the directory which contains the first distribution set you wish to install. This is either the directory you specified above, or possibly a subdirectory of that directory. When there, run "Set_tmp_dir" again, and choose the default temporary directory, by hitting return at the prompt. Run the "Extract" command, giving it as its sole argument the name of the distribution set you wish to extract. For example, to extract the base distribution, use the command: Extract base11 and to extract the games distribution: Extract game11 After the extraction is complete, go to the location of the next set you want to extract, "Set_tmp_dir" again, and once again issue the appropriate extract command. Continue this process until you've finished installing all of the sets which you desire to have on your hard disk. After each set is finished, if you know that you are running low on space you can remove the distribution files for that set by saying: rm set_name.?? For example, if you wish to remove the distribution files for the game09 set, after the "Extract game09" command has completed, issue the command: rm game11.?? Once you have extracted all sets and are at the "#" prompt again, proceed to the section "Configuring Your System," below. Configuring Your System: ----------- ---- ------ Once you have finished extracting all of the distribution sets that you want on your hard drive and are back at the "#" prompt, you are ready to configure your system. The configuration utility expects that you have installed the base system. If you have not, you will not be able to run it successfully (nor will you have a functional system regardless of configuration). To configure the newly installed operating system, run the command "Configure". Configure will ask for the machine's hostname, domain name, and other network configuration information. Once you have supplied `Configure' all that it requests, your machine will be configured well enough that when you reboot it it will almost be a completely functional NetBSD system. Note you should ignore the errors from `chown' they will be corrected shortly. Once you are done with `Configure', halt the system with the "halt" command (wait for "halted" to be displayed) and reboot. Then again boot NetBSD this time with the command: loadbsd netbsd You need to do your final tweeks now. First mount your file systems like so: mount -av Next you need to re-make your devices to get the ownership correct: cd /dev ./MAKEDEV all Your system is now complete but not completely configured; you should adjust the /etc/sendmail.cf file as necessary to suit your site and/or disable sendmail and other network related programs. These things can be found in /etc/netstart. Use vi, if you installed the man pages you can type `man vi' or `man ed' for instructions on how to use these somewhat non-intuitive editors. As mentioned at the end of the `Configure' run, you should copy the NetBSD kernel onto the root partition as "/netbsd". There is also another option to this. As NetBSD/Atari has to be booted from TOS, you could do the following: Reserve a small GEMDOS partition of about 4Mb. This is enough to put in a few kernels. Put the netbsd kernel into this partition. Also, edit your /etc/fstab to always mount this partition, say as /kernels. Now make a symlink from /netbsd to /kernels/netbsd. This sceme is particulary handy when you want to make your own kernel. When compilation is finished, you just copy your kernel to /kernels/netbsd and reboot. It's wise to make sure there is _always_ a 'know to work' kernel image present. To get the proper timezone settings, link /etc/localtime to the appropriate file in /usr/share/zoneinfo. The link provided is to /usr/share/zoneinfo/US/Pacific. Once you are done with the rest of configuration unmount your file systems and halt your system, then reboot: cd / umount -av halt <reboot> Finally you can now boot your system and it will be completely functional: loadbsd -a netbsd When it boots off of the hard drive, you will have a complete NetBSD system! CONGRATULATIONS! (You really deserve them!!!) Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ Before updating, you probably would want to backup your original filesystems! The update procedure will not overwrite or remove any files not present in the sets you install. If you've replaced programs present in the distribution, you have to replace them again after you did the update. The etc-set needs special caution. You generally don't want to install this one when upgrading. It is recommended that you get a copy of this set and _carefully_ upgrade your configuration files by hand. Before starting the actual procedure, make a note of the partitions your root- and usr-filesystems are on. You'll need to mount them by hand. Ok, let's go. Insert the bootfloppy and follow the 'normal' installation procedure until it asks you if you wish to proceed with the installation. Now enter 'n' and hit return. You will be left at the shell prompt. Now mount your root and usr filesystems on /mnt. If your root-filesystem is on sd1a and your usr-filesystem on sd1d this would require the following actions: mount_ffs /dev/sd1a /mnt mount_ffs /dev/sd1d /mnt/usr At this point, you can follow the section "Installing the NetBSD System" to install the sets. There is one difference: When Extract asks you "Are you installing a -current snapshot? [n]" answer 'y'. Once you are done installing the upgrade sets, then reboot: cd / umount -av halt <reboot> Now you can boot your upgraded system as usually, but take the new kernel! To finish up, you should rebuild your /dev-directory: cd /dev ./MAKEDEV all Administrivia: ------------- Registration? What's that? If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at <majordomo@NetBSD.ORG>. To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions. There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@NetBSD.ORG To report bugs, use the 'send-pr' command shipped with NetBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Additionally, bug reports can be sent by mail to: netbsd-bugs@NetBSD.ORG Use of 'send-pr' is encouraged, however, because bugs reported with it are entered into the NetBSD bugs database, and thus can't slip through the cracks. There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses. If you're interested in doing a serious amount of work on a specific port, you probably should contact the "owner" of that port (listed below). If you'd like to help with this effort, and have an idea as to how you could be useful, send mail and/or subscribe to: netbsd-help@NetBSD.ORG As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it. Thanks go to: ------ -- -- Members and former members of UCB's Computer Systems Research Group, including (but not limited to): Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick for their ongoing work on BSD systems, support, and encouragement. Also, our thanks go to: Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek for answering lots of questions, fixing bugs, and doing the various work they've done. UC Berkeley's Experimental Computing Facility provided a home for sun-lamp in the past, people to look after it, and a sense of humor. Rob Robertson, too, has added his unique sense of humor to things, and for a long time provided the primary FTP site for NetBSD. Without CVS, this project would be impossible to manage, so our hats go off to Brian Berliner, Jeff Polk, and the various other people who've had a hand in making CVS a useful tool. Alistair G. Crooks <agc@westley.demon.co.uk> has been producing tar file snapshot reports for NetBSD-current users, a very valuable service. Dave Burgess <burgess@cynjut.infonet.net> has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it. The following people (in alphabetical order) have made donations or loans of hardware and/or money, to support NetBSD development, and deserve credit for it: Jason Brazile Dave Burgess Charles Conn Canada Connect Corporation Brian Carlstrom Tom Coulter Charles D. Cranor Demon Internet, UK Greg Gingerich Michael L. Hitch Scott Kaplan Chris Legrow Herb Peyerl Mike Price Thor Lancelot Simon Bill Sommerfeld Paul Southworth Steve Wadlow (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.) Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in January, 1993. (Obviously, there are a lot more people who deserve thanks here. If you're one of them, and would like to mentioned, tell us!) We are: -- --- (in alphabetical order) The NetBSD core group: J.T. Conklin <jtc@NetBSD.ORG> Charles Hannum <mycroft@NetBSD.ORG> Paul Kranenburg <pk@NetBSD.ORG> The port-masters (and their ports): Allen Briggs <briggs@mail.vt.edu> (mac68k) Chuck Cranor <chuck@NetBSD.ORG> (mvme68k) Chris G. Demetriou <cgd@NetBSD.ORG> (alpha) Charles Hannum <mycroft@NetBSD.ORG> (1) Chris Hopps <chopps@NetBSD.ORG> (amiga) Paul Kranenburg <pk@NetBSD.ORG> (sparc) Ted Lemon <mellon@NetBSD.ORG> (pmax) Anders Magnusson <ragge@NetBSD.ORG> (vax) Phil Nelson <phil@NetBSD.ORG> (pc532) Gordon Ross <gwr@NetBSD.ORG> (sun3) Jason Thorpe <thorpej@NetBSD.ORG> (hp300) Leo Weppelman <leo@NetBSD.ORG> (atari) Supporting cast: Steve Allen <wormey@eskimo.com> John Brezak <brezak@NetBSD.ORG> Dave Burgess <burgess@cynjut.infonet.net> Hubert Feyrer <hubert.feyrer@rz.uni-regensburg.de> Adam Glass <glass@NetBSD.ORG> Brad Grantham <grantham@tenon.com> Matthew Green <mrg@eterna.com.au> Michael L. Hitch <osymh@gemini.oscs.montana.edu> Lawrence Kesteloot <kesteloo@cs.unc.edu> John Kohl <jtk@NetBSD.ORG> Paul Mackerras <paulus@NetBSD.ORG> Neil J. McRae <neil@domino.org> Perry Metzger <perry@NetBSD.ORG> Herb Peyerl <hpeyerl@beer.org> Matthias Pfaller <leo@marco.de> Chris Provenzano <proven@NetBSD.ORG> Waldi Ravens <waldi@moacs.indiv.nl.net> Scott Reynolds <scottr@edsi.org> Thor Lancelot Simon <tls@netbd.org> Wolfgang Solfrank <ws@tools.de> Frank van der Linden <fvdl@NetBSD.ORG> Christos Zoulas <christos@NetBSD.ORG> Legal Mumbo-jumbo: ----- ----- ----- The following notices are required to satisfy the license terms of the software that we have mentioned in this document: This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by the Computer Systems Engineering Group at Lawrence Berkeley Laboratory. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Adam Glass. This product includes software developed by Christian E. Hopps. This product includes software developed by Paul Kranenburg. This product includes software developed by John Kohl. This product includes software developed by Terrence R. Lambert. This product includes software developed by Frank van der Linden. This product includes software developed by Philip A. Nelson. This product includes software developed by Jochen Pohl. This product includes software developed by Chris Provenzano. This product includes software developed by Theo de Raadt. This product includes software developed by the David Muir Sharnoff. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed by Jason Thorpe. This product includes software developed by TooLs GmbH. This product includes software developed by Christos Zoulas. This product includes software developed by Christian E. Hopps. This product includes software developed by Gordon Ross This product includes software developed by Leo Weppelman. This product includes software developed by Markus Wild.